Skip to content

Conversation

link2xt
Copy link
Collaborator

@link2xt link2xt commented Sep 1, 2025

Split out of #7116

  • feat: do not set "unknown sender for this chat" error. We don't display if the group is protected in the UI already, so replacing messages with a square brackets error saying that sender is not verified is not needed. Protected groups are going to be removed completely later. Last commit is similar but for unverified contact that is a member of a chat.
  • fix: add "Messages are end-to-end encrypted." to non-protected groups. Previously the message was not added if you create an unprotected groups, this is just a bug. All encrypted chats should have such messages.
  • test: add TestContext.create_chat_id is an API for tests that I am going to use later, but it is already used by create_chat so can be seen as a refactoring.
  • Two more commits remove unused deprecated APIs.

@link2xt link2xt mentioned this pull request Sep 1, 2025
11 tasks
@link2xt link2xt requested review from Hocuri and iequidoo September 1, 2025 16:01
@link2xt link2xt force-pushed the link2xt/lypqsuxkxulr branch 2 times, most recently from 4ab43d6 to 355ceaa Compare September 1, 2025 16:28
@link2xt link2xt changed the title Various verified group fixes Various verified group changes Sep 1, 2025
@link2xt link2xt changed the title Various verified group changes Various protected group changes Sep 1, 2025
The messages are end-to-end encrypted
in encrypted group regardless
of whether the group is protected or not.
UIs now display green checkmark in a profile
if the contact is verified.
Chats with key-contacts cannot become unprotected,
so there is no need to check 1:1 chat.
@@ -1693,12 +1693,6 @@ async fn add_parts(
let name: &str = from.display_name.as_ref().unwrap_or(&from.addr);
for part in &mut mime_parser.parts {
part.param.set(Param::OverrideSenderDisplayname, name);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This usage of OverrideSenderDisplayname looks unnecessarily overloaded, i'd prefer we use smth else for this case. But maybe some translated string like "~non-member: NAME" would be good, at least this "~" won't cause confusion

@@ -422,7 +422,7 @@ pub enum Config {
/// Regardless of this setting, `chat.is_protected()` returns true while the key is verified,
/// and when the key changes, an info message is posted into the chat.
/// 0=Nothing else happens when the key changes.
/// 1=After the key changed, `can_send()` returns false and `is_protection_broken()` returns true
/// 1=After the key changed, `can_send()` returns false
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How can this happen now?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This actually cannot happen to key-contacts. We should remove this setting, it is only used in get_info() for logging its value.

@link2xt link2xt merged commit 7ea6ca3 into main Sep 2, 2025
29 checks passed
@link2xt link2xt deleted the link2xt/lypqsuxkxulr branch September 2, 2025 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants